Provisioning - Automatically create spaces

As a part of provisioning you can create spaces for users.

On the Automatically create spaces tab you can see all space templates that have been defined, and you can see which subsets of users will have spaces created with each template.

You can also create new space templates, and you can define which space templates to use to automatically create spaces. You can do this by setting up rules that map groups of users to space templates along with details of how space names and video addresses should be generated.

Add rules for automatically creating spaces

To define a rule:

  1. Click Add rule.
  2. Choose a user import from the User import drop-down.

  3. Optional: Add a Filter to specify a smaller group of these users if you want to provision the same type of space to only some of them.

    You can leave the field blank if you want to provision the same type of space to all of the users in the chosen subset.

  4. Define a Space name mapping.

    This defines a rule for how the space name will be generated. For instance, if you enter $cn$'s space, and a user's Common Name is Sally Wood, then this user's space will be named Sally Wood's space.

    Note: The LDAP attribute name is case sensitive.

  5. Define a URI user part mapping.

    This defines a rule for how the URIs for the space are defined. For instance, if you enter $sAMAccountName$, and a user's SAM account name is swood, and the domain for the user is example.com, then the URIs will be swood@example.com, swood.host@example.com, or similar, depending on how the unique URI generator for a role is defined.

    Note: The LDAP attribute used in the URI user part mapping must be unique for the user.

    Note: It is possible to use more than one LDAP attribute in the URI user part mapping. If you use more than one LDAP attribute, then make sure that at least one of them is unique for the user.

    Note: The Meeting Server will convert attribute values to lower case. No other characters are removed or modified (including spaces), so make sure that the URI user part mapping will result in a URI that can be used for all users.

  6. Under Choose a space template, choose Create new template or choose an existing one.

    If you chose an existing template, click Done and ignore the following steps.

    If you chose Create new template, click Create space template and continue to step 7.

  7. Define a Template name.

    Note: This name is also what users see in the Cisco Meeting Server web app. Make sure that you choose a name that would make sense to ordinary app users.

  8. Write a space Template description.

    Note: This description is also seen in the web app, and they choose space templates based on this description. Make sure that you write a description that is easy for ordinary app users to understand.

  9. Decide if different roles should be differentiated by their passcode, or if they should each have a unique URI and Meeting ID.
  10. Click Add role

  11. Enter a Role name.

    Note: Make sure that the name is descriptive so app users can guess from the name what this role is.

  12. From the Visibility drop-down, choose the visibility scope for the template.

  13. Enter a Unique URI generator to define a rule for how the Meeting Server should generate the URI that participants with this role should use to access the space.

    The URIs are created based on the URI user part mapping, the URI generator, and the domain. For example, if you entered $.host, and the URI user part mapping is $givenName$.space, then a space for someone named Sally created on the domain example.com will have the URI sally.space.host@example.com.

    Note: This field is disabled if you chose to use the same URI for all roles.

  14. Define the minimum passcode length.

    If you ignore this setting, Meeting Management will choose to use the system default. If you do not want to require a passcode, then enter 0.

    Note: The system default is 0, unless your Meeting Server administrator has set a different default on system or tenant level.

    Note: If you have chosen to use the same URI and numeric ID for all roles, and there is more than one role, then you can only set one role to have no passcode. If you set more than one role to have no passcode, then the Meeting Server will ignore your setting for these and provide a 4 character passcode for them.

  15. Click Next.

  16. Check the Make role and Activator check box if you want participants with this role to be Activators.

    An Activator is a participant who can start a meeting. For information about scenarios where this is relevant, see Use the meeting lobby or lock a meeting

  17. Define permissions for the role.

    To use the system value for a setting, leave the Override check box unchecked.

    To define a new setting, check the Override check box and choose the value that you want from the following options:

    Table 18: Options available while defining permissions for the role
    Field name Description
    Maximum participants Set a maximum number of active participants in the meeting.
    Recording mode

    Choose one of the following options:

    Disable: Recording is disabled

    Manual: Users can start and stop recordings

    Automatic: All meetings in the space are recorded
    Locked by default Set if all meetings in this space will start locked.
    Passcode timeout (seconds) Set the number of seconds the Meeting Server will wait for participants to enter a passcode when prompted before falling back to a role without passcode. To disable the timeout, enter a value of 0.
    Video allowed Set whether to allow participant video in meetings in this space. Sharing presentation video is always allowed, even for audio-only meetings.
    Default video layout Set the default video layout seen by participants in this meeting.
    Behaviour when last activator leaves The experience of remaining participants in the meeting when the last Activator leaves.
    Allow change role Participants with this permission can change role
  18. Click Next.
  19. Repeat steps 10-18 until you have added all the roles you want in this space template.

  20. Use Default for dial out to select a default role for dial out participants during the meeting.

  21. Click Next.

  22. Define default settings for the space.

    To use the system value for a setting, leave the Override check box unchecked.

    To define a new setting, check the Override check box and choose the value that you want.

  23. Click Done.

Note: Your changes will not be applied before you have committed them. After you have committed the changes, template settings will take effect immediately. Changes to LDAP server details and any changes that affect users will take effect next time the Meeting Server is synchronized with the LDAP servers.

Note: All changes to provisioning settings that you have entered in Meeting Management will be lost if you restart Meeting Management before the changes have been committed.